Conversation
6 new issues
|
| } | ||
| } | ||
| } | ||
| window.addEventListener('keydown', this.langMenuKeydownHandler, true) |
| e.stopImmediatePropagation() | ||
| this.onLangMenuKeydown(e) | ||
| } | ||
| } |
| this.closeLangMenu() | ||
| break | ||
| } | ||
| } |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2017 +/- ##
=========================================
Coverage 70.07% 70.07%
Complexity 1703 1703
=========================================
Files 34 34
Lines 4484 4484
=========================================
Hits 3142 3142
Misses 1342 1342 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
d2e1e60 to
c82a48d
Compare
|
Rebased to issue1889-vocab-search-a11y-fixes and force pushed. |
UnniKohonen
left a comment
There was a problem hiding this comment.
Keyboard navigation seems to work correctly for the most part and screen reader messages seem to be correct.
There were a couple of issues I noticed:
Both global and vocab search have a problem in firefox where if tab is pressed when focused on dropdown options, focus moves to the next field and then immediately back. This causes the screen reader to read both aria labels. It seems like this issue was not present previously so it should be maybe fixed. In chrome, tab moves focus to the next dropdown option which is probably fine.
Dropdown chevrons have moved in the wrong position. These rules should be included for the .chevron class to fix the problem:
right: 1rem;
top: 50%;
transform: translate(0, -50%);
and for .dropdown-toggle:
padding-right: 2.5rem
Vocab search language dropdown hover and focus effects have also changed. If this is not intentional, they should be fixed (it seems to be at least partially because language selection list no longer has the language-list id).
There is also a failing cypress test in vocab search page but it probably doesn't originate from this PR.
I cannot reproduce this behavior in Firefox or Chrome. I get the expected bahavior where tab moves the focus to the next menu, as intended.
Thanks! Fixed as suggested.
That was not intentional. Thanks for spotting it (I wish we had tests for CSS too). Fixed.
|
Reasons for creating this PR
Link to relevant issue(s), if any
Description of the changes in this PR
This PR should be based upon PR #2004 as it improves the keyboard navigation on top of the previous accessibility improvements.
Known problems or uncertainties in this PR
Checklist
.sr-onlyclass, color contrast)